Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1198

reference: 523-tree-1
name: 1198
tree-preservation-order: undefined
523-tpo-1
uprn
address-text
point: POINT (-1.018467 50.899016)
geometry: MULTIPOLYGON (((-1.018424 50.899011,-1.018426 50.899020,-1.018432 50.899027,-1.018441 50.899033,-1.018453 50.899037,-1.018466 50.899039,-1.018492 50.899034,-1.018501 50.899028,-1.018507 50.899020,-1.018510 50.899012,-1.018508 50.899004,-1.018502 50.898996,-1.018493 50.898990,-1.018481 50.898986,-1.018468 50.898985,-1.018454 50.898986,-1.018442 50.898990,-1.018433 50.898996,-1.018427 50.899003,-1.018424 50.899011)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL